Summary

• Bug Fix: Fix SLAS client update command failing when updating only scopes (fixes SLAS Client Update Does not Fully Upsert #41)
• New Feature: Add slas client open command to open the SLAS Admin UI in browser

Details

Bug #41 Fix

The SLAS API returns redirectUri as a pipe-delimited string (e.g., "url1|url2|url3") but the PUT endpoint expects an array of individual URLs. The update command was wrapping the entire pipe-delimited string as a single array element instead of splitting it.

Before:

"redirectUri": ["http://localhost:3000/callback|http://localhost:3000/social-callback"]

After:

"redirectUri": ["http://localhost:3000/callback", "http://localhost:3000/social-callback"]

New slas client open Command

Opens the SLAS Admin UI in the browser, deep-linking to a specific client:

b2c slas client open <clientId> --tenant-id <tenantId>

URL pattern: https://{shortCode}.api.commercecloud.salesforce.com/shopper/auth-admin/v1/ui/client?clientId={clientId}&tenantId={tenantId}

Test plan

• Run b2c slas client update --scopes <scope> <clientId> --tenant-id <tenantId> on a client with existing redirect URIs
• Run b2c slas client open <clientId> --tenant-id <tenantId> and verify browser opens to correct URL
• Run pnpm run build to verify compilation
• Run pnpm --filter @salesforce/b2c-cli run lint to verify linting passes